Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/components/image-preview-cell.js`:
- Around line 26-27: The filename decoding step for resolvedFileName can throw
on malformed percent-encodings; wrap the decodeURIComponent call that uses
imageUrl.split("/").pop().split("?")[0] in a safe guard: try to decode and on
any exception fall back to the raw segment (or a sanitized fallback like an
empty string); update the expression that assigns resolvedFileName (refer to
resolvedFileName, imageUrl) to use this safe decode logic so render-time errors
are avoided.

In `@src/pages/sponsors-global/form-templates/form-template-item-list-page.js`:
- Around line 209-213: The render callback currently destructures file_url from
row.images[0] which can throw if the first array element is nullish; update the
render implementation used for the column to read the URL via optional chaining
(e.g., access row.images?.[0]?.file_url) before calling isImageUrl, and only
return <ImagePreviewCell imageUrl={url} /> when url is a valid string and
isImageUrl(url) is true; keep the checks around row.images length/existence and
use the same symbols (render, row.images, isImageUrl, ImagePreviewCell) so the
change is localized to that render function.

In `@src/utils/methods.js`:
- Around line 637-641: getFileUploadAllowedExtensions currently returns raw
tokens without trimming, so inputs like "jpg, png,   " produce entries with
whitespace; update the function (getFileUploadAllowedExtensions) to normalize
tokens by mapping each element (whether coming from an array or from
String(ext).split(",")) through .toString()/String(...) then .trim(), and then
filter(Boolean) to remove empty strings—i.e., convert ext to an array, trim
every item, and filter out falsy values before returning.

---

Nitpick comments:
In `@src/components/__tests__/image-preview-cell.test.js`:
- Around line 40-54: Add a new test in
src/components/__tests__/image-preview-cell.test.js that renders
<ImagePreviewCell> without a fileName but with an imageUrl whose last path
segment contains a malformed percent-encoding (e.g., "%E0%A4%A"), then simulate
the click on the preview button and assert the component does not crash and
shows a filename/fallback; specifically, reuse the existing test pattern
(userEvent.setup(), render(<ImagePreviewCell imageUrl={badUrl} />), await
user.click(screen.getByRole("button", { name: title }))) and assert the UI
contains either a safe fallback or the raw segment using a tolerant matcher (for
example
expect(screen.getByText(/sponsor_banner\.png|%E0%A4%A/)).toBeInTheDocument()),
so the test verifies resilience of ImagePreviewCell's filename extraction logic.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/pages/sponsors-global/inventory/inventory-list-page.js`:
- Around line 172-180: The render function for the image cell currently only
reads row.images?.[0]?.file_url which can be undefined even when
row.images?.[0]?.file_path exists; update the imageUrl assignment in the render
(the variable used when rendering ImagePreviewCell) to use a fallback: imageUrl
= row.images?.[0]?.file_url ?? row.images?.[0]?.file_path, and adjust the
hasImages/imageUrl existence check so the ImagePreviewCell is rendered when
either URL or file_path is present while keeping itemName unchanged.

---

Nitpick comments:
In `@src/pages/sponsors-global/inventory/inventory-list-page.js`:
- Around line 173-177: The hasImages boolean is redundant because imageUrl
already uses optional chaining; remove the hasImages declaration and simplify
the guard to only check imageUrl (i.e., drop the Array.isArray(row.images) &&
row.images.length > 0 check and keep the existing imageUrl logic). Locate the
block using variables hasImages, imageUrl, and itemName in
inventory-list-page.js and delete the hasImages line and the combined if
(!hasImages || !imageUrl) guard, replacing it with a single if (!imageUrl)
return null to preserve behavior.